Curse

Inskipp · Dec 16, 2007, 02:56 AM // 02:56

I saw this problem a while back, and a video driver update fixed it, but it looks like its back. I'm just wondering if its an nvidia problem again, or if its something I can fix with a setting.

Here's what it looks like. Note the areas around the paths, especially further away.

Full size image: http://home.comcast.net/~king_of_the...gw_glitch1.jpg

Here are my specs:
EVGA 680i mainboard
Intel [email protected]
2GB RAM
Nvidia 7900GT/512MB ram, driver version: 169.21
Windows XP pro sp2

In the game, I run 1650x1050 resolution, I have on 4xAA, and all the graphics settings on high, and my visual quality slider is set on highest quality. I've tried changing all the in-game stuff, turning post-processing on and off, and trying all kinds of different settings. I tried making a couple changes in my driver's settings too, but nothing I found helped.

I remember seeing this problem back when I had the 91.?? driver, but switching to a 93.?? driver fixed it. I'm not sure when it came back, since I update all the time, but I'd rather use the latest driver I can.

Any suggestions are appreciated!

Yanman.be · Dec 16, 2007, 11:07 AM // 11:07

Seems like it doesn't update the high-res textures as it should be. I'll test it later myself on the same spot.

Maybe forcing AF on in the NVidia panel might smooth things a bit?

Inskipp · Dec 27, 2007, 02:22 AM // 02:22

This happens everywhere I go. Its just very evident in those screenshots.

This kinda stinks, since it was an issue before, was solved, and has now come back. I guess I'll post in the guru3d forums and see what turns up, I can't be the only one having this issue.

Jade Barbosa · Dec 27, 2007, 02:36 AM // 02:36

have you got the "use best texture filtering" setting in the game turned on? That looks like its the game degrading the graphics in the distance, not something that would be influenced by drivers really.

Inskipp · Dec 27, 2007, 05:45 PM // 17:45

Sure do. The only reason I think its a driver issue is because it happened before. It was acknowledged and fixed. Now its back, so I would assume that its a driver issue again, but I might be wrong.